Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invert the expected denoise_mask parameter to the FLUX Denoise node #6853

Merged
merged 1 commit into from
Sep 13, 2024

Conversation

RyanJDick
Copy link
Collaborator

Invert the expected denoise_mask parameter to the FLUX Denoise node to match the behaviour of Denoise Latents node used for SD.

Summary

Changes the definition of the denoise_mask parameter on the "FLUX Denoise" node to match the "Denoise Latents" node. New definition: "Values of 0.0 represent the regions to be fully denoised, and 1.0 represent the regions to be preserved."

Also updates the docs in a few places to make this expectation more clear.

QA Instructions

I tested on top of this branch: #6846

Checklist

  • The PR has a short but descriptive title, suitable for a changelog
  • Tests added / updated (if applicable)
  • Documentation added / updated (if applicable)

…o match the behaviour of Denoise Latents node used for SD.
@github-actions github-actions bot added python PRs that change python files invocations PRs that change invocations labels Sep 13, 2024
@hipsterusername hipsterusername merged commit 51df5aa into main Sep 13, 2024
14 checks passed
@hipsterusername hipsterusername deleted the ryan/fix-flux-denoise-mask-definition branch September 13, 2024 21:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invocations PRs that change invocations python PRs that change python files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants